User plane integrity protection

ABSTRACT

A method performed by a user equipment, UE, for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network is provided. The method includes sending a session establishment request towards a session management node that includes an indication of a user plane integrity protection mode supported by the UE. The method further includes receiving an activation message from a receiving radio access node that includes an indication to the UE to activate the user plane integrity protection mode for a data radio bearer established with the receiving radio access node. Methods performed by a session management node, a target access and mobility node, and a radio access node are also provided.

TECHNICAL FIELD

The present disclosure relates generally to wireless communications systems and, more particularly user plane integrity protection in a wireless network.

BACKGROUND

The 3GPP TS 23.501 describes the 5G network architecture. A stripped down simplified version of a 5G network is shown in FIG. 1.

A UE (User Equipment) is a mobile device used by a user to wirelessly access the network. The radio access network (RAN) function or base station, e.g. gNB (Next Generation Node B), is responsible for providing wireless radio communication to the UE and connecting the UE to the core network. A core network function, e.g. AMF (Access and Mobility Management Function), is responsible for handling the mobility of the UE, among other responsibilities. Another core network function, e.g. SMF (Session Management Function), is responsible for handling the session and traffic steering of the UE, among other responsibilities. Yet another core network function, e.g. UPF (User Plane Function) is responsible for interconnecting to data network, packet routing and forwarding, among other responsibilities.

The RAN in 5G (called NG-RAN) has another type of base station that may be referred to as a ng-eNB. This is an evolved LTE (Long Term Evolution) eNB (e Node B) connected to a 5G Core.

The UE interacts with the ng-eNB or the gNB over-the-air using radio interface. The radio interface traffic includes control plane traffic and user plane traffic. The radio control plane is also called RRC (Radio Resource Control). The ng-eNB or the gNB in turn may interact with the AMF using an N2 interface. An N11 interface may be between the AMF and the SMF. Similarly, an ng-eNB or a gNB and an UPD may interact using an N3 interface. There may not be a direct interface between an ng-eNB or gNB and a SMF and, therefore, they may interact via the AMF.

SUMMARY

According to some embodiments of the present disclosure, a method performed by a user equipment, UE, for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network are provided. The method includes sending a session establishment request towards a session management node that includes an indication of a user plane integrity protection mode supported by the UE. The method further includes receiving an activation message from a receiving radio access node that includes an indication to the UE to activate the user plane integrity protection mode for a data radio bearer established with the receiving radio access node. In some embodiments, the radio access node is an evolved long term evolution radio access node.

According to other embodiments of the present disclosure, a method performed by a UE for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network are provided. The method includes sending (1500) a registration request to a target core node that includes an indication that the UE supports a user plane integrity protection mode for communicating with a radio access node. In some embodiments, the method performed by the UE further includes receiving a request from the target core node to resend the registration request including the indication that the UE supports the user plane integrity protection mode. In some embodiments, the radio access node is an evolved long term evolution radio access node.

According to other embodiments of the present disclosure, a method performed by a session management node for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network is provided. The method includes receiving a session establishment request from a user equipment, UE, that includes an indication of a user plane integrity protection mode supported by the UE. In some embodiments, the radio access node is an evolved long term evolution radio access node.

In some embodiments of the present disclosure, the method performed by the session management node further includes sending a session request to a core node that includes the user plane integrity protection mode supported by the UE.

According to other embodiments of the present disclosure, a method performed by a target access and mobility node for enabling user plane integrity protection of data during a mobility registration update procedure in a packet data convergence protocol, PDCP, in a radio access network is provided. The method includes receiving a registration request from a user equipment, UE, that includes an indication that the UE supports a user plane integrity protection mode for communicating with a radio access node.

In some embodiments of the present disclosure, the method performed by the target access and mobility node further includes receiving a message from a source access and mobility node that includes the indication that the UE supports a user plane integrity protection mode. In some embodiments, the radio access node is an evolved long term evolution radio access node.

According to other embodiments of the present disclosure, a method performed by a radio access node for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network is provided. The method includes receiving a session information request from a core node that includes an indication of a user plane integrity protection mode supported by a user equipment, UE.

In some embodiments of the present disclosure, the method performed by the radio access node further includes sending an activation message to the UE that includes the indication to the UE to activate user plane integrity protection for a data radio bearer established with a receiving radio access node. In some embodiments, the radio access node is an evolved long term evolution radio access node.

Corresponding embodiments of inventive concepts for a UE, a session management node, a target access and mobility node, a radio access node, computer products, and computer programs are also provided.

The following explanation of potential problems with existing solutions is a present realization as part of the present disclosure and is not to be construed as previously known by others. There is no support for the integrity protection of user plane in PDCP in a Rel-15 ng-eNB in Option 4, Option 5 and Option 7 of Rel-15. There is only support in Rel-15 for the integrity protection of user plane in NR (new radio) PDCP (Packet Data Convergence Protocol) in a Rel-15 gNB. All interfaces between a Rel-15 UE, a Rel-15 5G core network and a Rel-15 ng-eNB have been prepared in Rel-15 to enable the integrity protection of a user plane in a Rel-15 ng-eNB in Option 4, Option 5 and/or Option 7. A Rel-15 UE was not able to test user plane integrity protection in PDCP with a ng-eNB in Option 4, Option 5 and Option 7 in a real or live Rel-15 network. Therefore, a Rel-15 UE may not be enabled to use user plane integrity protection in PDCP with a Rel-16 ng-eNB.

Operational advantages that may be provided by one or more embodiments of the present disclosure may include user plane integrity protection (UP IP) of data sent in PDCP protocol between a UE and a ng-eNB may be enabled and used in Option 4, Option 5 and/or Option 7. As a consequence, for example, an advantage of enablement and use of UP IP in Option 4, 5, and/or 7 may be that the receiving side (UE or ng-eNB) may be able to detect if an attacker altered or modified received user data traffic.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in a constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:

FIG. 1 illustrates a simplified 5G network, Option 4, from Rel-15;

FIG. 2 illustrates a simplified 5G network, Option 5, from Rel-15;

FIG. 3 illustrates a simplified 5G network, Option 7, from Rel-15;

FIG. 4 illustrates operations to configure network devices during a PDU Session Establishment Request to enable user plane integrity protection of data in PDCP, in accordance with some embodiments of the present disclosure;

FIG. 5 illustrates operations to configure network devices during a Service Request procedure to enable user plane integrity protection of data in PDCP, in accordance with some embodiments of the present disclosure;

FIG. 6 illustrates operations to configure network devices during a Registration Request to enable user plane integrity protection of data in PDCP, in accordance with some embodiments of the present disclosure;

FIG. 7 illustrates operations to configure network devices during a Service Request procedure to enable user plane integrity protection of data in PDCP, in accordance with some embodiments of the present disclosure;

FIG. 8 illustrates operations to configure network devices during a mobility registration update-N10 interface procedure to enable user plane integrity protection of data in PDCP, in accordance with some embodiments of the present disclosure;

FIG. 9 illustrates operations to configure network devices during a mobility N2 HO-N10 interface procedure to enable user plane integrity protection of data in PDCP, in accordance with some embodiments of the present disclosure;

FIG. 10 illustrates operations to configure network devices during a mobility Xn HO-Xn interface procedure to enable user plane integrity protection of data in PDCP, in accordance with some embodiments of the present disclosure;

FIG. 11 illustrates operations to configure network devices during dual connectivity-Xn interface to enable user plane integrity protection of data in PDCP, in accordance with some embodiments of the present disclosure;

FIGS. 12-17 are flowcharts of operations that may be performed by a UE, in accordance with some embodiments of the present disclosure;

FIGS. 18-19 are flowcharts of operations that may be performed by a session management node, in accordance with some embodiments of the present disclosure;

FIGS. 20-24 are flowcharts of operations that may be performed by an access and mobility node, in accordance with some embodiments of the present disclosure;

FIGS. 25-31 are flowcharts of operations that may be performed by a radio access node, in accordance with some embodiments of the present disclosure;

FIG. 32 is a block diagram of elements of a UE that are configured according to some embodiments of the present disclosure;

FIG. 33 is a block diagram of elements of a radio access node that are configured according to some embodiments of the present disclosure;

FIG. 34 is a block diagram of elements of a session management node that are configured according to some embodiments of the present disclosure;

FIG. 35 is a block diagram of elements of an access and mobility node that are configured according to some embodiments of the present disclosure;

FIG. 36 is a block diagram of a wireless network in accordance with some embodiments of the present disclosure;

FIG. 37 is a block diagram of a user equipment or other terminal in accordance with some embodiments of the present disclosure;

FIG. 38 is a block diagram of a virtualization environment in accordance with some embodiments of the present disclosure;

FIG. 39 is a block diagram of a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments of the present disclosure;

FIG. 40 is a block diagram of a host computer communicating via a base station with a user equipment user equipment or other terminal over a partially wireless connection in accordance with some embodiments of the present disclosure;

FIG. 41 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment user equipment or other terminal in accordance with some embodiments of the present disclosure;

FIG. 42 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment user equipment or other terminal in accordance with some embodiments of the present disclosure;

FIG. 43 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment user equipment or other terminal in accordance with some embodiments of the present disclosure; and

FIG. 44 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment user equipment or other terminal in accordance with some embodiments of the present disclosure.

DETAILED DESCRIPTION

Inventive concepts will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment.

The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as teaching examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, certain details of the described embodiments may be modified, omitted, or expanded upon without departing from the scope of the described subject matter. The term “terminal” is used in a non-limiting manner and, as explained below, can refer to any type of radio communication terminal. The term “terminal” herein may be interchangeable replaced with the term “radio terminal,” “radio communication terminal,” “radio device,” or “user equipment (UE).”

In one approach, the ng-eNB may be connected to the AMF as shown, for example, in FIG. 1 (which is a simplified version of Option 5 in Rel-15).

In another approach, the gNB may act as a master node in Dual Connectivity. The gNB may be connected to the AMF via the N2 interface. The ng-eNB may act as the secondary node in Dual Connectivity and may be connected to the gNB via the Xn interface as shown, for example, in FIG. 2 (which is a simplified version of Option 4 in Rel-15).

In another approach, the ng-eNB may act as a master node in Dual Connectivity. The ng-eNB may be connected to the AMF via the N2 interface. The gNB may act as the secondary node in Dual Connectivity and may be connected to the ng-eNB via the Xn interface as shown, for example in FIG. 3 (which is a simplified version of Option 7 in Rel-15).

The logical aspects between the UE and the AMF may be referred to as NAS (non-access stratum); and the logical aspects between the UE and the gNB may be referred to as AS (access stratum). Correspondingly, the security of communication (control plane and user plane, if applicable) may be referred to as NAS security and AS security, respectively.

The AS security may include confidentiality and integrity protection of the control plane (e.g., the RRC) and the user plane traffic. Radio bearers in AS that carry control plane or RRC messages may be referred to as a signaling data bearer (SRB). Similarly, radio bearers in AS that carry user plane messages may be referred to as a data bearer (DRB).

In an LTE system (Long Term Evolution, which is popularly known as 4G), AS security may be mandatory for both the RRC and the user plane; which may mean that both confidentiality and integrity protection are activated for the RRC and confidentiality is activated for the user plane. There is no support for integrity protection of the user plane in LTE. While there are null-encryption and null-integrity algorithms in LTE, null-encryption and null-integrity algorithms in LTE do not encrypt and integrity protect the RRC or user plane traffic. Because these null algorithms are a type of algorithm, AS security may be said to be activated, e.g., activated using null algorithms.

In a 5G system, AS security is mandatory for the RRC but it is optional for the user plane. This may mean that both confidentiality and integrity protection will be activated for the RRC, however, confidentiality and integrity protection are optional for the user plane.

In 5G, AS user plane (UP) security activation has been decoupled from AS control plane (CP) security activation. The AS CP security is activated by a run of the AS Security Mode Command (SMC) procedure which is a roundtrip of RRC messages between a UE and a RAN node. The procedure may allow the negotiation of the cryptographic algorithms, the establishment of the ciphering and integrity protection keys, and the activation of the secure mode of the protocol. While the activation of AS CP security happens at the run of AS SMC procedure, the activation of the UP security in 5G takes place during another RRC signaling (called RRC reconfiguration procedure) between a UE and a RAN node (gNB or ng-eNB).

As explained above, there is no support for the integrity protection of user plane in PDCP in a Rel-15 ng-eNB in Option 4, Option 5 and Option 7 of Rel-15 shown, for example in FIGS. 1-3. There is only support in Rel-15 for the integrity protection of user plane in NR PDCP in a Rel-15 gNB.

All interfaces between a Rel-15 UE, a Rel-15 5G core network and a Rel-15 ng-eNB have been prepared in Rel-15 to enable the integrity protection of a user plane in a Rel-15 ng-eNB in Option 4, Option 5 and/or Option 7.

A Rel-15 UE was not able to test user plane integrity protection in PDCP (Packet Data Convergence Protocol) with a ng-eNB in Option 4, Option 5 and Option 7 in a real or live Rel-15 network. Therefore, a Rel-15 UE may not be enabled to use user plane integrity protection in PDCP with a Rel-16 ng-eNB. The 5G network Rel-16, therefore, may need to be able to distinguish between Rel-16 UE's and Rel-15 UE's.

In various embodiments of inventive concepts, in a 5G system, user plane integrity protection (UP IP) of data sent in PDCP protocol between a UE and a ng-eNB may be enabled and used in Option 4, Option 5 and/or Option 7. An advantage of enablement and use of UP IP in Option 4, 5, and/or 7 may be that the receiving side (UE or ng-eNB) may be able to detect if an attacker altered or modified received user data traffic.

As used herein, reference to an evolved long term evolution radio access node includes, e.g., an E-UTRA node (also referred to as a ng-eNB or a Next Generation Evolved Node-B as referenced, e.g., in 3GPP TS 33.501). An ng-eNB is an enhanced LTE/4G eNB that connects to a 5G Core Network via NG interfaces but still uses LTE/4G air interfaces to communicate with a 5G UE. As used herein, reference to a next generation radio access node B includes, e.g., a gNB (also referred to a new radio access node). As used herein, reference to a long term evolution eNode B includes, e.g., an LTE eNB (also referred to as a 4G Node B).

In various embodiments of inventive concepts, an indication of a UP IP mode supported by a UE, for example: UE_UP_IP_NG_ENB may be provided (referred to herein as UP IP mode). The UP IP mode may include that:

UE supports UP IP in LTE PDCP with a radio access node (e.g., ng-eNB) in 5G networks at a full data rate

Or

UE supports UP IP in PDCP with the radio access node (e.g., ng-eNB) in 5G networks at a defined rate that is less than the full data rata. The defined rate may include any rate that is less than a full data rate.

In one embodiment of inventive concepts, UP IP is enabled during, e.g., a PDU Session Establishment Request as illustrated in FIG. 4. FIG. 4 illustrates operations to configure network devices during a PDU Session Establishment Request to enable user plane integrity protection of data in PDCP. As shown in FIG. 4, at 402, UE 102 initiates a PDU Session Establishment procedure with SMF 108 to establish bearers with the network and includes indicator UE_UP_IP_NG_ENB into a PDU Session Establishment Request message. UE_UP_IP_NG_ENB indicates that UE 102 supports User Plane integrity protection in LTE PDCP. UE_UP_IP_NG_ENB can also indicate the UE's defined data rate for UP integrity protection.

At 404, SMF 108 initiates a N2 PDU Session Request procedure with ng-eNB 104 and can include UE security capability UE_UP_IP_NG_ENB to ng-eNB 104.

At 406, ng-eNB 104 initiates a RRC Reconfiguration procedure with UE 102 and can indicate to UE 102 to activate UP integrity protection for DRBs (data radio bearers) established with ng-eNB 104.

At 408, a RRC Reconfiguration procedure may occur between UE 102 and ng-eNB 104 that can include ng-eNB 104 sending to UE 102 an indication to activate the UP IP mode for a data radio bearer established with ng-eNB.

These and other related operations are now described in the context of the operational flowcharts of FIGS. 12, 18, and 25. FIG. 12 is a flowchart of operations that can be performed by a UE. FIG. 18 is a flowchart of operations that can be performed by a session management node. FIG. 25 is a flowchart of operations that can be performed by a radio access node.

Referring initially to FIG. 12, operations can be performed by a UE (e.g., 3200 in FIG. 32) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include sending 1200 a session establishment request to a session management node that includes an indication of a user plane integrity protection mode supported by a UE. The UP IP mode may be as described above.

In at least some embodiments, the operations further include receiving 1202 an activation message from a receiving radio access node that includes an indication to the UE to activate the user plane integrity protection mode for a data radio bearer established with receiving radio access node.

The receiving radio access node can be a long term evolution radio access node.

Referring to the example embodiment of FIG. 18, operations can be performed by a session management node (e.g., 3400 in FIG. 34) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include receiving 1800 a session establishment request from a UE that includes an indication of a user plane integrity protection mode supported by the UE. The UP IP mode may be as described above.

The radio access node can be a long term evolution radio access node.

Referring to the example embodiment of FIG. 25, operations can be performed by a radio access node (e.g., 3300 in FIG. 33) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include receiving 2500 a session information request from a core node that includes an indication of a user plane integrity protection mode supported by a UE. The UP IP mode may be as described above.

The core node can be an AMF node (e.g., AMF 106; AMF 3500 of FIG. 35).

The radio access node can be a long term evolution radio access node.

In at least some embodiments, the operations further include sending an activation message to the UE that includes the indication to the UE to activate user plane integrity protection for a data radio bearer established with a receiving radio access node.

The receiving radio access node can be a long term evolution radio access node.

In a further embodiment of inventive concepts, UP IP can be enabled during, e.g., a Service Request procedure as illustrate in FIG. 5. As shown in FIG. 5, at 502, UE 102 initiates a Service Request procedure with AMF 106 to re-establish data bearers with the network.

At 504, AMF 106 initiates a Nsmf_PDUSession_UpdateSMContext Request with SMF 108.

At 506, SMF 108 initiates a Namf_Communication_N1NwMessageTransfer with AMF 106 and can include UE 102 security capability in indicator UE_UP_IP_NG_ENB.

At 508, AMF 106 initiates a N2 PDU Session Request procedure with ng-eNB 104 and forwards UE 102 security capability in indicator UE_UP_IP_NG_ENB to ng-eNB 104.

At 510, ng-eNB 104 initiates a RRC Reconfiguration procedure with UE 102 and can indicate to UE 102 to activate UP integrity protection for DRBs (data radio bearers) established with ng-eNB 104.

These and other related operations are now described in the context of the operational flowcharts of FIGS. 13, 19, and 25. FIG. 13 is a flowchart of operations that can be performed by a UE. FIG. 19 is a flowchart of operations that can be performed by a session management node. FIG. 25 is a flowchart of operations that can be performed by a radio access node.

Referring initially to FIG. 13, operations can be performed by a UE (e.g., 3200 in FIG. 32) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include sending 1300 a service request to a core node to establish a data radio bearer with the radio access network. The operations further include receiving 1302 an activation message from a receiving radio access node that includes an indication to the UE to activate a user plane integrity protection mode for the data radio bearer established with the receiving radio access node. The UP IP mode may be as described above.

The core node can be an AMF node (e.g., AMF 106; AMF 3500 of FIG. 35).

The radio access node can be a long term evolution radio access node.

The receiving radio access node can be a long term evolution radio access node.

Referring to the example embodiment of FIG. 19, operations can be performed by a session management node (e.g., 3400 in FIG. 34) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include sending 1900 a session management information transfer message to a core node that includes a user plane integrity mode of a UE. The UP IP mode may be as described above.

The core node can be an AMF node (e.g., AMF 106; AMF 3500 of FIG. 35).

The radio access node can be a long term evolution radio access node.

Referring to the example embodiment of FIG. 25, operations can be performed by a radio access node (e.g., 3300 in FIG. 33) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network, as described with reference to FIG. 25 above.

In another embodiment of inventive concepts, UP IP can be enabled during, e.g., a Registration Request as illustrated in FIG. 6. As shown in FIG. 6, at 602, UE 102 registers to the 5G network and includes indicator UE_UP_IP_NG_ENB into a Registration Request message. UE_UP_IP_NG_ENB can indicate that UE 102 supports User Plane integrity protection in PDCP when communicating with ng-eNB 104. UE_UP_IP_NG_ENB can also indicate a defined data rate of UE 102 for UP integrity protection.

At 604, AMF 106 initiates an Authentication procedure and/or NAS Security Mode Command procedure to establish security between UE 102 and AMF 106.

At 606, AMF 106 initiates an Initial Context Setup procedure with ng-eNB 104 and can include UE 102 security capability in indicator UE_UP_IP_NG_ENB to ng-eNB 104.

At 608, ng-eNB 104 initiates an AS SMC (AS Security Mode Command) procedure with UE 102. No DRB's may be established with UE 102.

These and other related operations are now described in the context of the operational flowcharts of FIGS. 14, 20, and 26. FIG. 14 is a flowchart of operations that can be performed by a UE. FIG. 20 is a flowchart of operations that can be performed by an access and mobility node. FIG. 26 is a flowchart of operations that can be performed by a radio access node.

Referring initially to FIG. 14, operations can be performed by a UE (e.g., 3200 in FIG. 32) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include sending 1400 a registration request to a radio access node that includes an indication that the UE supports a user plane integrity protection mode for communicating with the radio access node. The UP IP mode may be as described above.

The radio access node can be a long term evolution radio access node.

Referring to the example embodiment of FIG. 27, operations can be performed by an access and mobility node (e.g., 3500 in FIG. 35) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include receiving (2000) a registration request from a UE that includes an indication that the UE supports a user plane integrity protection mode for communicating with a radio access node. The UP IP mode may be as described above.

The radio access node can be a long term evolution radio access node.

In at least some embodiments, the operations further include sending 2002 a setup procedure request to a setup radio access node that includes the indication that the UE supports a user plane integrity protection mode.

The setup radio access node can be an evolved long term evolution radio access node (e.g. E-UTRA nodes: ng-eNB).

Referring to the example embodiment of FIG. 26, operations can be performed by a radio access node (e.g., 3300 in FIG. 33) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include receiving 2600 a setup request from a core node that includes an indication that the UE supports a user plane integrity protection mode for communicating with radio access node. The UP IP mode may be as described above.

The core node can be an AMF node (e.g., AMF 106; AMF 3500 of FIG. 35).

The radio access node can be a long term evolution radio access node.

In another embodiment of inventive concepts, UP IP can be enabled in another Service Request procedure as illustrated in FIG. 7. As shown in FIG. 7, at 702, UE 102 initiates a Service Request procedure with AMF 106 to re-establish data bearers with the network.

At, 704, AMF 106 initiates a Nsmf_PDUSession_UpdateSMContext Request with SMF 108.

At 706, SMF 108 initiates a Namf_Communication_N1NwMessageTransfer with AMF 106.

At 708, AMF 106 initiates a N2 PDU Session Request procedure with ng-eNB 104 and can include UE 102 security capability in indicator UE_UP_IP_NG_ENB to ng-eNB 104.

At 710, ng-eNB 104 initiates a RRC Reconfiguration procedure with UE 102 and can indicate to UE 102 to activate UP integrity protection for DRBs (data radio bearers) established with ng-eNB 104.

These and other related operations are now described in the context of the operational flowcharts of FIGS. 13 and 25. FIG. 13 is a flowchart of operations that can be performed by a UE. FIG. 25 is a flowchart of operations that can be performed by an access and mobility node.

Referring initially to FIG. 13, operations can be performed by a UE (e.g., 3200 in FIG. 32) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include sending 1300 a service request to a core node to establish a data radio bearer with the radio access network. The operations further include receiving 1302 an activation message from a receiving radio access node that includes an indication to the UE to activate a user plane integrity protection mode for the data radio bearer established with the receiving radio access node. The UP IP mode may be as described above.

The core node can be an AMF node (e.g., AMF 106; AMF 3500 of FIG. 35).

The radio access node can be a long term evolution radio access node.

The receiving radio access node can be a long term evolution radio access node.

Referring to the example embodiment of FIG. 25, operations can be performed by a radio access node (e.g., 3300 in FIG. 33) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network, as described with reference to FIG. 25 above.

In another embodiment of inventive concepts, UP IP can be enabled during, e.g., a mobility registration update over a N10 interface as illustrated in FIG. 8. As shown in FIG. 8, at 802, UE 102 registers to the 5G network and can include UE_UP_IP_NG_ENB into a Registration Request message. UE_UP_IP_NG_ENB can indicate that UE 102 supports User Plane integrity protection in PDCP when communicating with ng-eNB 104. UE_UP_IP_NG_ENB can also indicate a defined data rate of UE 102 for UP integrity protection.

At 804, target AMF 106 a contacts source AMF 106 b and can include the complete Registration Request.

At 806, source AMF 106 b provides UE 102 security capabilities e.g. UE_UP_IP_NG_ENB, if stored and if Registration Request is successfully authenticated, to target AMF 106 a.

At 808, target AMF 106 a initiates a NAS Security Mode Command with ng-eNB 104 if the Registration Request was not successfully integrity protected and can request UE 102 to resend a Registration Request including UE 102 security capability in indicator UE_UP_IP_NG_ENB.

These and other related operations are now described in the context of the operational flowcharts of FIGS. 15, 21, and 23. FIG. 15 is a flowchart of operations that can be performed by a UE. FIG. 21 is a flowchart of operations that can be performed by a source access and mobility node. FIG. 23 is a flowchart of operations that can be performed by a target access and mobility node.

Referring initially to FIG. 15, operations can be performed by a UE (e.g., 3200 in FIG. 32) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include sending 1500 a registration request to a target core node that includes an indication that the UE supports a user plane integrity protection mode for communicating with a radio access node. The UP IP mode may be as described above.

The target core node can be an AMF node (e.g., AMF 106; AMF 3500 of FIG. 35).

In at least some embodiments, the operations further include receiving 1502 a request from the target core node to resend the registration request including the indication that the UE supports the user plane integrity protection mode.

The radio access node can be a long term evolution radio access node.

Referring to the example embodiment of FIG. 21, operations can be performed by a source access and mobility node (e.g., 3500 in FIG. 35) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include receiving 2100 a registration request for a user equipment, UE, from a target access and mobility node that includes an indication that the UE supports a user plane integrity protection mode for communicating with a radio access node provided that the user plane integrity protection mode is stored in the source access and mobility node. The UP IP mode may be as described above.

The operations further include, if the registration request is successfully authenticated at the source access and mobility node, sending 2102 a message to the target access mobility node that includes the user plane integrity protection mode.

The source core node can be an AMF node (e.g., AMF 106 b; AMF 3500 of FIG. 35).

The target core node can be an AMF node (e.g., AMF 106 a; AMF 3500 of FIG. 35).

The radio access node can be a long term evolution radio access node.

Referring to the example embodiment of FIG. 23, operations can be performed by a radio access node (e.g., 3300 in FIG. 33) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include receiving 2300 a registration request from a UE that includes an indication that the UE supports a user plane integrity protection mode for communicating with a radio access node. The UP IP mode may be as described above.

The radio access node can be a long term evolution radio access node.

In at least some embodiments, the operations further include receiving 2302 a message from a source access and mobility node that includes the indication that the UE supports a user plane integrity protection mode.

The source access and mobility node can be an AMF node (e.g., AMF 106 b; AMF 3500 of FIG. 35).

In another embodiment of inventive concepts, UP IP is enabled during, e.g., during a mobility N2 handover-N10 interface as illustrated in FIG. 9. As shown in FIG. 9, at 902, source ng-eNB 104 a/gNB 104 b initiates a handover (HO) Required with source AMF 106 b.

At 904, source AMF 106 b initiates a Forward Relocation Request with target AMF 106 a and forwards UE_UP_IP_NG_ENB if stored in source AMF 106 b to target AMF 106 a.

At 906, target AMF 106 a initiates a HO Command Request to target ng-eNB 104 c and includes UE_UP_IP_NG_ENB if stored in target AMF 106 a to target ng-eNB 104 c.

At 908, target ng-eNB 104 c selects security algorithms and indicates to UE 102 to activate UP IP for DRBs established with ng-eNB 104 b.

At 910, target AMF 106 a forwards information received in 908 from target ng-eNB 104 c to source AMF 106 b.

At 912, source AMF 106 b forwards information received in 910 from target AMF 106 a to source ng-eNB 104 a or gNB 104 b.

At 914, source ng-eNB 104 a or gNB 104 b forwards information received in 912 from source AMF 106 a to UE 102.

UE 102 activates UP IP for DRB's established with target ng-eNB 104 c.

These and other related operations are now described in the context of the operational flowcharts of FIGS. 16, 22, 24, 27 and 29. FIG. 16 is a flowchart of operations that can be performed by a UE. FIG. 22 is a flowchart of operations that can be performed by a source access and mobility node. FIG. 24 is a flowchart of operations that can be performed by a target access and mobility node. FIG. 27 is a flowchart of operations that can be performed by a source radio access node. FIG. 29 is a flowchart of operations that can be performed by a target radio access node.

Referring initially to FIG. 16, operations can be performed by a UE (e.g., 3200 in FIG. 32) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include receiving 1600 a handover command from a source radio access node that includes an indication to the UE to activate a user plane integrity protection mode for a data radio bearer established with a target radio access node. The UP IP mode may be as described above.

The operations further include activating 1602 the user plane integrity protection mode for the data radio bearer established with the target radio access node.

The radio access node can be a long term evolution radio access node.

The source radio access node can be one of: an evolved long term evolution radio access node (e.g. E-UTRA nodes: ng-eNB) and a next generation radio access node B (e.g. gNB).

The target radio access node can be one of: an evolved long term evolution radio access node and a next generation node B.

Referring to the example embodiment of FIG. 22, operations can be performed by a source access and mobility node (e.g., 3500 in FIG. 35) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include receiving 2200 a relocation request from a target access and mobility node that includes a user plane integrity protection mode of a UE. The UP IP mode may be as described above.

The radio access node can be a long term evolution radio access node.

In at least some embodiments, the operations further include sending 220) a handover command to a target radio access node that includes the user plane integrity protection mode.

The operations further include receiving 2204 a response to the handover command from the target radio access node that includes an indication to the UE to activate user plane integrity protection for a data radio bearer established with the target radio access node; and sending 2206 a response to the relocation request to the target access and mobility node that includes the indication to the UE to activate user plane integrity protection for a data radio bearer established with the target radio access node.

The target radio access node can be one of: an evolved long term evolution radio access node and a next generation node B.

Referring to the example embodiment of FIG. 24, operations can be performed by a target access and mobility node (e.g., 3500 in FIG. 35) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include sending 2400 a relocation request to a source access and mobility node that includes a user plane integrity protection mode of a user equipment. The UP IP mode may be as described above.

The radio access node can be an evolved long term evolution radio access node.

In at least some embodiments, the operations can further include receiving 2402) a response to the relocation request from the source access and mobility node that includes an indication to the UE to activate user plane integrity protection for a data radio bearer established with the target radio access node. The operations can further include sending 2404 a handover command to a source radio access node that includes the indication to the UE to activate user plane integrity protection for the data radio bearer established with the target radio access node.

The source radio access node can be one of: an evolved long term evolution radio access node and a next generation node B.

Referring to the example embodiment of FIG. 27, operations can be performed by a source radio access node (e.g., 3300 in FIG. 33) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include receiving 2700 a handover command from a target core node that includes an indication to a UE to activate a user plane integrity protection mode for a data radio bearer established with the target radio access node. The UP IP mode may be as described above.

The operations further include sending 2702 an activation message to the UE that includes an indication to the UE to activate the user plane integrity protection mode for the data radio bearer established with the target radio access node.

The radio access node can be an evolved long term evolution radio access node.

The source radio access node can be one of: an evolved long term evolution radio access node and a next generation node B.

The target radio access node can be one of: an evolved long term evolution radio access node and a next generation node B.

Referring to the example embodiment of FIG. 29, operations can be performed by a target radio access node (e.g., 3300 in FIG. 33) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include receiving 2900 a handover command from a source core node that includes an indication to a UE to activate a user plane integrity protection mode for a data radio bearer established with the target radio access node. The UP IP mode may be as described above.

In at least some embodiments, the operations can further include sending 2902 a response to the handover command to the source core node that includes an indication to the UE to activate the user plane integrity protection mode for a data radio bearer established with the target radio access node.

The target radio access node can be one of: an evolved long term evolution radio access node and a next generation node B.

The radio access node can be an evolved long term evolution radio access node.

The source core node can be an AMF node (e.g., AMF 106 b; AMF 3500 of FIG. 35).

The target core node can be an AMF node (e.g., AMF 106 a; AMF 3500 of FIG. 35).

In another embodiment of inventive concepts, UP IP can be enabled during, e.g., during a mobility Xn handover-Xn interface as illustrated in FIG. 10. As shown in FIG. 10, at 1002, source ng-eNB 104 a/gNB 104 b initiate a HO Required with target ng-eNB 104 c and include indicator UE_UP_IP_NG_ENB.

At 1004, target ng-eNB 104 c can select security algorithms and, based on indicator UE_UP_IP_NG_ENB, may indicate to UE 102 to activate UP IP for DRBs established with ng-eNB 104 c.

At 1006, source ng-eNB 104 a/gNB 104 b forwards information received in 1004 from target ng-eNB 104 c to UE 102.

UE 102 can activate UP IP for DRB's established with target ng-eNB 104 c.

These and other related operations are now described in the context of the operational flowcharts of FIGS. 16, 22, 27, 28 and 30. FIG. 16 is a flowchart of operations that can be performed by a UE. FIG. 22 is a flowchart of operations that can be performed by a source access and mobility node. FIG. 27 is a flowchart of operations that can be performed by a source radio access node. FIG. 28 is a flowchart of operations that can be performed by a source radio access node. FIG. 30 is a flowchart of operations that can be performed by a target radio access node.

Referring initially to FIG. 16, operations can be performed by a UE (e.g., 3200 in FIG. 32) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include the operations described above with reference to FIG. 16.

Referring to the example embodiment of FIG. 22, operations can be performed by a source access and mobility node (e.g., 3500 in FIG. 35) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include the operations described above with reference to FIG. 22.

Referring to the example embodiment of FIG. 27, operations can be performed by a source radio access node (e.g., 3300 in FIG. 33) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include the operations described above with reference to FIG. 27.

Referring to the example embodiment of FIG. 28, operations can be performed by a source radio access node (e.g., 3300 in FIG. 33) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include sending 2800 a handover command request to a target radio access node that includes an indication that a UE supports a user plane integrity protection mode for communicating with a radio access node. The UP IP mode may be as described above.

In at least some embodiments, the operations further include receiving 2802 a response to the handover command request from the target radio access node that includes an indication to the UE to activate the user plane integrity protection mode for a data radio bearer established with the target radio access node.

In at least some further embodiments, the operations further include sending 2804 a handover command to the UE that includes an indication to the UE to activate the user plane integrity protection mode for a data radio bearer established with the target radio access node.

The radio access node can be an evolved long term evolution radio access node.

The source radio access node can be one of: an evolved long term evolution radio access node and a next generation node B

The target radio access node can be one of: an evolved long term evolution radio access node and a next generation node B.

Referring to the example embodiment of FIG. 30, operations can be performed by a source radio access node (e.g., 3300 in FIG. 33) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include receiving 3000 a handover command request from a source radio access node that includes an indication that a UE supports a user plane integrity protection mode for communicating with a radio access node. The UP IP mode may be as described above.

In at least some embodiments, the operations further include sending 3002 a response to the handover command request to the source radio access node that includes an indication to the UE to activate the user plane integrity protection mode for a data radio bearer established with the target radio access node.

The source radio access node can be one of: an evolved long term evolution radio access node and a next generation node B

The target radio access node can be one of: an evolved long term evolution radio access node and a next generation node B.

The radio access node can be an evolved long term evolution radio access node.

In another embodiment of inventive concepts, for Option 4, UP IP can be enabled during, e.g., dual connectivity-Xn interface as illustrated in FIG. 11. As shown in FIG. 11, at 1102, Master Node (MN) in Dual Connectivity (ng-eNB 104 e or gNB 104 f) initiates a secondary node (SN) Addition/Modification procedure with Secondary Node (SN) (ng-eNB 104 g) and indicates UE_UP_IP_NG_ENB to SN 104 g.

At 1104, SN ng-eNB 104 g selects security algorithms and, based on UE_UP_IP_NG_ENB, can decide to indicate to UE 102 to activate UP IP for DRBs established with ng-eNB 104 e. SN 104 g can send a SN Addition/Modification Response including selected algorithms and may indicate to UE 102 to activate UP IP for DRBs established with ng-eNB 104 e.

At 1106, Master Node in Dual Connectivity (ng-eNB 104 e or gNB 104 f) initiates a RRC Reconfiguration procedure with UE 102 and forwards the information received in 1104 from SN ng-eNB 104 g to UE 102.

UE 102 can activate UP IP for DRB's established with secondary node ng-eNB 104 g.

These and other related operations are now described in the context of the operational flowcharts of FIGS. 17 and 31. FIG. 17 is a flowchart of operations that can be performed by a UE. FIG. 31 is a flowchart of operations that can be performed by a master node.

Referring initially to FIG. 17, operations can be performed by a UE (e.g., 3200 in FIG. 32) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include receiving (1700) an activation message from a master node that includes an indication to the UE to activate a user plane integrity protection mode for a data radio bearer established with a secondary node. The UP IP mode may be as described above.

In at least some embodiments, the operations further include activating 1702 the user plane integrity protection mode for the data radio bearer established with the secondary node.

The radio access node can be an evolved long term evolution radio access node.

The master node can be one of: an evolved long term evolution radio access node and a next generation node B.

The secondary node can be one of: an evolved long term evolution radio access node and a next generation node B.

Referring to the example embodiment of FIG. 31, operations can be performed by a master radio access node (e.g., 3300 in FIG. 33) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The operations include sending 3100 a message to a secondary node that includes an indication that a UE supports a user plane integrity protection mode for communicating with a radio access node. The UP IP mode may be as described above.

In at least some embodiments, the operations further include, based on the user plane integrity protection mode, deciding 3102 to indicate to the UE to activate user plane integrity protection for a data radio bearer established with a secondary node. The operations can further include sending 3104 a response to the message to the master node that includes an indication to the UE to activate the user plane integrity protection mode for the data radio bearer established with the secondary node.

The master node can be one of: an evolved long term evolution radio access node and a next generation node B.

The secondary node can be one of: an evolved long term evolution radio access node and a next generation node B.

The radio access node can be an evolved long term evolution radio access node.

FIG. 32 is a block diagram illustrating a UE 3200 that is configured according to some embodiments. The UE 3200 can include, without limitation, a wireless terminal, a wireless communication device, a wireless communication terminal, a terminal node/UE/device, etc. The UE 3200 includes a RF front-end 3230 comprising one or more power amplifiers the transmit and receive through antennas of an antenna array 3240 to provide uplink and downlink radio communications with a radio network node (e.g., a base station, eNB, gNB, a ng-eNB, etc.) of a telecommunications network. UE 3200 further includes a processor circuit 3210 (also referred to as a processor) coupled to the RF front end 3230 and a memory circuit 3220 (also referred to as memory). The memory 3220 stores computer readable program code that when executed by the processor 3210 causes the processor 3210 to perform operations according to embodiments disclosed herein.

FIG. 33 is a block diagram illustrating a radio access node 3300 (e.g., a base station, eNB, gNB, a ng-eNB, a source node, a target, a master node, a secondary node, etc.) of a radio access network (e.g., a 5G radio access network). The radio access node 3300 includes a processor circuit 3310 (also referred to as a processor), a memory circuit 3320 (also referred to as memory), and a network interface 3350 (e.g., wired network interface and/or wireless network interface) configured to communicate with other network nodes. The radio access node 3300 may be configured as a radio network node containing a RF front end with one or more power amplifiers 3330 that transmit and receive through antennas of an antenna array 3340. The memory 3320 stores computer readable program code that when executed by the processor 3310 causes the processor 3310 to perform operations according to embodiments disclosed herein.

FIG. 34 is a block diagram illustrating a session management node 3400 (e.g., a SMF, a source SMF, a target SMF, etc.) of a radio access network (e.g., a 5G radio access network). The session management node 3400 includes a processor circuit 3410 (also referred to as a processor), a memory circuit 3420 (also referred to as memory), and a network interface 3450 (e.g., wired network interface and/or wireless network interface) configured to communicate with other network nodes. The memory 3420 stores computer readable program code that when executed by the processor 3410 causes the processor 3410 to perform operations according to embodiments disclosed herein.

FIG. 35 is a block diagram illustrating an access and mobility node 3500 (e.g., a AMF, a source AMF, a target AMF, etc.) of a radio access network (e.g., a 5G radio access network). The access and mobility node 3500 includes a processor circuit 3510 (also referred to as a processor), a memory circuit 3520 (also referred to as memory), and a network interface 3550 (e.g., wired network interface and/or wireless network interface) configured to communicate with other network nodes. The memory 3520 stores computer readable program code that when executed by the processor 3510 causes the processor 3510 to perform operations according to embodiments disclosed herein.

References include TS 33.501 and TS 23.401.

Listing of Embodiments: Example Embodiments are discussed below. Reference numbers/letters are provided in parenthesis by way of example/illustration without limiting example embodiments to particular elements indicated by reference numbers/letters.

Embodiment 1. A method performed by a user equipment, UE, for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The method includes sending (1200) a session establishment request to a session management node that includes an indication of a user plane integrity protection mode supported by the UE. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with a radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.

Embodiment 2. The method of Embodiment 1, further including: receiving (1202) an activation message from a receiving radio access node that includes an indication to the UE to activate the user plane integrity protection mode for a data radio bearer established with the receiving radio access node.

Embodiment 3. The method of Embodiment 1, wherein the radio access node is an evolved long term evolution radio access node.

Embodiment 4. The method of Embodiment 2, wherein the receiving radio access node is an evolved long term evolution radio access node.

Embodiment 5. A method performed by a user equipment, UE, for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The method includes sending (1300) a service request to a core node to establish a data radio bearer with the radio access network. The method further includes receiving (1302) an activation message from a receiving radio access node that includes an indication to the UE to activate a user plane integrity protection mode for the data radio bearer established with the receiving radio access node. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with a radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.

Embodiment 6. The method of Embodiment 5, wherein the radio access node is an evolved long term evolution radio access node.

Embodiment 7. The method of Embodiment 5, wherein the receiving radio access node is an evolved long term evolution radio access node.

Embodiment 8. A method performed by a user equipment, UE, for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The method includes sending (1400) a registration request to a radio access node that includes an indication that the UE supports a user plane integrity protection mode for communicating with the radio access node. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with the radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.

Embodiment 9. The method of Embodiment 8, wherein the radio access node is an evolved long term evolution radio access node.

Embodiment 10. A method performed by a user equipment, UE, for enabling user plane integrity protection of data during a mobility registration update procedure in a packet data convergence protocol, PDCP, in a radio access network. The method includes sending (1500) a registration request to a target core node that includes an indication that the UE supports a user plane integrity protection mode for communicating with a radio access node. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with the radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.

Embodiment 11. The method of Embodiment 10, further including receiving (1502) a request from the target core node to resend the registration request including the indication that the UE supports the user plane integrity protection mode.

Embodiment 12. The method of Embodiment 10, wherein the radio access node is an evolved long term evolution radio access node.

Embodiment 13. A method performed by a user equipment, UE, for enabling user plane integrity protection of data during a mobility procedure in a packet data convergence protocol, PDCP, in a radio access network. The method includes receiving (1600) a handover command from a source radio access node that includes an indication to the UE to activate a user plane integrity protection mode for a data radio bearer established with a target radio access node. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with a radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate; and activating (1602) the user plane integrity protection mode for the data radio bearer established with the target radio access node.

Embodiment 14. The method of Embodiment 13, wherein the radio access node is an evolved long term evolution radio access node.

Embodiment 15. The method of Embodiment 13, wherein the source radio access node is one of: an evolved long term evolution radio access node and a next generation radio access node B.

Embodiment 16. The method of Embodiment 13, wherein the target radio access node is one of: an evolved long term evolution radio access node and a next generation node B.

Embodiment 17. A method performed by a user equipment, UE, for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a dual connectivity radio access network. The method includes receiving (1700) an activation message from a master node that includes an indication to the UE to activate a user plane integrity protection mode for a data radio bearer established with a secondary node. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with a radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.

Embodiment 18. The method of Embodiment 17, further including activating (1702) the user plane integrity protection mode for the data radio bearer established with the secondary node.

Embodiment 19. The method of Embodiment 17, wherein the radio access node is an evolved long term evolution radio access node.

Embodiment 20. The method of Embodiment 17, wherein the master node is one of: an evolved long term evolution radio access node and a next generation node B.

Embodiment 21. The method of any of Embodiments 17 to 18, wherein the secondary node is an evolved long term evolution radio access node.

Embodiment 22. A method performed by a session management node for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The method includes receiving (1800) a session establishment request from a user equipment, UE, that includes an indication of a user plane integrity protection mode supported by the UE. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.

Embodiment 23. The method of Embodiment 22, wherein the radio access node is an evolved long term evolution radio access node.

Embodiment 24. The method of any of Embodiments 22 to 23, further including sending (1802) a session request to a core node that includes the user plane integrity protection mode supported by the UE.

Embodiment 25. A method performed by a session management node for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The method includes sending (1900) a session management information transfer message to a core node that includes a user plane integrity mode of a user equipment, UE. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with a radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.

Embodiment 26. The method of Embodiment 25, wherein the radio access node is an evolved long term evolution radio access node.

Embodiment 27. A method performed by an access and mobility node for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The method includes receiving (2000) a registration request from a user equipment, UE, that includes an indication that the UE supports a user plane integrity protection mode for communicating with a radio access node. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with the radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.

Embodiment 28. The method of Embodiment 27, wherein the radio access node is an evolved long term evolution radio access node.

Embodiment 29. The method of any of Embodiments 26 to 27, further including sending (2002) a setup procedure request to a setup radio access node that includes the indication that the UE supports a user plane integrity protection mode.

Embodiment 30. The method of Embodiment 29, wherein the setup radio access node is an evolved long term evolution radio access node.

Embodiment 31. A method performed by a source access and mobility node for enabling user plane integrity protection of data during a mobility registration update procedure in a packet data convergence protocol, PDCP, in a radio access network. The method includes receiving (2100) a registration request for a user equipment, UE, from a target access and mobility node that includes an indication that the UE supports a user plane integrity protection mode for communicating with a radio access node provided that the user plane integrity protection mode is stored in the source access and mobility node. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with the radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate; and if the registration request is successfully authenticated at the source access and mobility node, sending (2102) a message to the target access mobility node that includes the user plane integrity protection mode.

Embodiment 32. The method of Embodiment 31, wherein the radio access node is an evolved long term evolution radio access node.

Embodiment 33. A method performed by a source access and mobility node for enabling user plane integrity protection of data during a mobility procedure in a packet data convergence protocol, PDCP, in a radio access network. The method includes receiving (2200) a relocation request from a target access and mobility node that includes a user plane integrity protection mode of a user equipment, UE. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with a radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.

Embodiment 34. The method of Embodiment 33, wherein the radio access node is an evolved long term evolution radio access node.

Embodiment 35. The method of any of Embodiments 33 to 34, further including sending (2202) a handover command to a target radio access node that includes the user plane integrity protection mode. The method further includes receiving (2204) a response to the handover command from the target radio access node that includes an indication to the UE to activate user plane integrity protection for a data radio bearer established with the target radio access node. The method further includes sending (2206) a response to the relocation request to the target access and mobility node that includes the indication to the UE to activate user plane integrity protection for a data radio bearer established with the target radio access node.

Embodiment 36. The method of Embodiment 35, wherein the target radio access node is one of: an evolved long term evolution radio access node and a next generation node B.

Embodiment 37. A method performed by a target access and mobility node for enabling user plane integrity protection of data during a mobility registration update procedure in a packet data convergence protocol, PDCP, in a radio access network. The method includes receiving (2300) a registration request from a user equipment, UE, that includes an indication that the UE supports a user plane integrity protection mode for communicating with a radio access node. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with the radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.

Embodiment 38. The method of Embodiment 37, wherein the radio access node is an evolved long term evolution radio access node.

Embodiment 39. The method of any of Embodiments 37 to 38, further including receiving (2302) a message from a source access and mobility node that includes the indication that the UE supports a user plane integrity protection mode.

Embodiment 40. A method performed by a target access and mobility node for enabling user plane integrity protection of data during a mobility registration update procedure in a packet data convergence protocol, PDCP, in a radio access network. The method includes sending (2400) a relocation request to a source access and mobility node that includes a user plane integrity protection mode of a user equipment, UE. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with a radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.

Embodiment 41. The method of Embodiment 40, wherein the radio access node is an evolved long term evolution radio access node.

Embodiment 42. The method of any of Embodiments 40 to 41, further including receiving (2402) a response to the relocation request from the source access and mobility node that includes an indication to the UE to activate user plane integrity protection for a data radio bearer established with the target radio access node. The method further includes sending (2404) a handover command to a source radio access node that includes the indication to the UE to activate user plane integrity protection for the data radio bearer established with the target radio access node.

Embodiment 43. The method of Embodiment 42, wherein the source radio access node is one of: an evolved long term evolution radio access node and a next generation node B.

Embodiment 44. A method performed by a radio access node for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The method includes receiving (2500) a session information request from a core node that includes an indication of a user plane integrity protection mode supported by a user equipment, UE. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.

Embodiment 45. The method of Embodiment 44, wherein the radio access node is an evolved long term evolution radio access node.

Embodiment 46. The method of any of Embodiments 44 to 45, further including sending (2502) an activation message to the UE that includes the indication to the UE to activate user plane integrity protection for a data radio bearer established with a receiving radio access node.

Embodiment 47. The method of Embodiment 46, wherein the receiving access node is an evolved long term evolution radio access node.

Embodiment 48. A method performed by a radio access node for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The method includes receiving (2600) a setup request from a core node that includes an indication that the UE supports a user plane integrity protection mode for communicating with radio access node. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with the radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.

Embodiment 49. The method of Embodiment 48, wherein the radio access node is an evolved long term evolution radio access node.

Embodiment 50. A method performed by a source radio access node for enabling user plane integrity protection of data during a mobility procedure in a packet data convergence protocol, PDCP, in a radio access network. The method includes receiving (2700) a handover command from a target core node that includes an indication to a user equipment, UE, to activate a user plane integrity protection mode for a data radio bearer established with the target radio access node. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with a radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate. The method further includes sending (2702) an activation message to the UE that includes an indication to the UE to activate the user plane integrity protection mode for the data radio bearer established with the target radio access node.

Embodiment 51. The method of Embodiment 50, wherein the radio access node is an evolved long term evolution radio access node.

Embodiment 52. The method of Embodiment 50, wherein the source radio access node is one of: an evolved long term evolution radio access node and a next generation node B.

Embodiment 53. The method of Embodiment 50, wherein the target radio access node is one of: an evolved long term evolution radio access node and a next generation node B.

Embodiment 54. A method performed by a source radio access node for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a dual connectivity radio access network. The method includes sending (2800) a handover command request to a target radio access node that includes an indication that a user equipment, UE, supports a user plane integrity protection mode for communicating with a radio access node. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with the radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.

Embodiment 55. The method of Embodiment 54, further including receiving (2802) a response to the handover command request from the target radio access node that includes an indication to the UE to activate the user plane integrity protection mode for a data radio bearer established with the target radio access node.

Embodiment 56. The method of any of Embodiments 54 to 55, further including sending (2804) a handover command to the UE that includes an indication to the UE to activate the user plane integrity protection mode for a data radio bearer established with the target radio access node.

Embodiment 57. The method of Embodiment 54, wherein the radio access node is an evolved long term evolution radio access node.

Embodiment 58. The method of Embodiment 54, wherein the source radio access node is one of: an evolved long term evolution radio access node and a next generation node B.

Embodiment 59. The method of any of Embodiments 54 to 56, wherein the target radio access node is one of: an evolved long term evolution radio access node and a next generation node B.

Embodiment 60. A method performed by a target radio access node for enabling user plane integrity protection of data during a mobility procedure in a packet data convergence protocol, PDCP, in a radio access network. The method includes receiving (2900) a handover command from a source core node that includes an indication to a user equipment, UE, to activate a user plane integrity protection mode for a data radio bearer established with the target radio access node. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.

Embodiment 61. The method of Embodiment 60, further including sending (2902) a response to the handover command to the source core node that includes an indication to the UE to activate the user plane integrity protection mode for a data radio bearer established with the target radio access node.

Embodiment 62. The method of any of Embodiments 60 to 61, wherein the target radio access node is one of: an evolved long term evolution radio access node and a next generation node B.

Embodiment 63. The method of Embodiment 60, wherein the radio access node is an evolved long term evolution radio access node.

Embodiment 64. A method performed by a target radio access node for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a dual connectivity radio access network. The method including receiving (3000) a handover command request from a source radio access node that includes an indication that a user equipment, UE, supports a user plane integrity protection mode for communicating with a radio access node. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with the radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.

Embodiment 65. The method of Embodiment 64, further including sending (3002) a response to the handover command request to the source radio access node that includes an indication to the UE to activate the user plane integrity protection mode for a data radio bearer established with the target radio access node.

Embodiment 66. The method of any of Embodiments 64 to 65, wherein the source radio access node is one of: an evolved long term evolution radio access node and a next generation node B.

Embodiment 67. The method of any of Embodiments 64 to 65, wherein the target radio access node is one of: an evolved long term evolution radio access node and a next generation node B.

Embodiment 68. The method of Embodiment 64, wherein the radio access node is an evolved long term evolution radio access node

Embodiment 69. A method performed by a master node for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a dual connectivity radio access network. The method includes sending (3100) a message to a secondary node that includes an indication that a user equipment, UE, supports a user plane integrity protection mode for communicating with a radio access node. The user plane integrity protection mode includes one of: the UE supports user plane integrity protection in PDCP with the radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.

Embodiment 70. The method of Embodiment 69, further including based on the user plane integrity protection mode, deciding (3102) to indicate to the UE to activate user plane integrity protection for a data radio bearer established with a secondary node. The method further includes sending (3104) a response to the message to the master node that includes an indication to the UE to activate the user plane integrity protection mode for the data radio bearer established with the secondary node.

Embodiment 71. The method of any of Embodiments 69 to 70, wherein the master radio access node is one of: an evolved long term evolution radio access node and a next generation node B.

Embodiment 72. The method of any of Embodiments 64 to 65, wherein the secondary radio access node is an evolved long term evolution radio access node.

Embodiment 73. The method of Embodiment 69, wherein the radio access node is an evolved long term evolution radio access node.

Embodiment 74. The method of any of Embodiments 1 to 73, wherein the radio access network is a 5G network.

Embodiment 75. A user equipment (3200) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The user equipment includes a processor (3210); and a memory (3220) coupled to the processor, wherein the memory stores instructions that when executed by the processor causes the processor to perform operations according to any of Embodiments 1 to 21.

Embodiment 76. A computer program product, including a non-transitory computer readable storage medium including computer readable program code embodied in the medium that when executed by a processor (3210) of a user equipment (3200) causes the processor to perform operations according to any of Embodiments 1 to 21.

Embodiment 77. A session management node (3400) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The session management node including a processor (3410); and a memory (3420) coupled to the processor, wherein the memory stores instructions that when executed by the processor causes the processor to perform operations according to any of Embodiments 22 to 26.

Embodiment 78. A computer program product, including a non-transitory computer readable storage medium including computer readable program code embodied in the medium that when executed by a processor (3410) of a session management node (3400) causes the processor to perform operations according to any of Embodiments 22 to 26.

Embodiment 79. An access and mobility node (3500) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The access and mobility node including a processor (3510); and a memory (3520) coupled to the processor, wherein the memory stores instructions that when executed by the processor causes the processor to perform operations according to any of Embodiments 27 to 30.

Embodiment 80. A computer program product, including a non-transitory computer readable storage medium comprising computer readable program code embodied in the medium that when executed by a processor (3510) of an access and mobility node (3500) causes the processor to perform operations according to any of Embodiments 27 to 30.

Embodiment 81. A source access and mobility node (3500) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The source access and mobility node including a processor (3510); and a memory (3520) coupled to the processor, wherein the memory stores instructions that when executed by the processor causes the processor to perform operations according to any of Embodiments 31 to 36.

Embodiment 82. A computer program product, including a non-transitory computer readable storage medium comprising computer readable program code embodied in the medium that when executed by a processor (3510) of a source access and mobility node (3500) causes the processor to perform operations according to any of Embodiments 31 to 36.

Embodiment 83. A target access and mobility node (3500) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The target access and mobility node including a processor (3510); and a memory (3520) coupled to the processor, wherein the memory stores instructions that when executed by the processor causes the processor to perform operations according to any of Embodiments 37 to 43.

Embodiment 84. A computer program product, including a non-transitory computer readable storage medium including computer readable program code embodied in the medium that when executed by a processor (3510) of a target access and mobility node (3500) causes the processor to perform operations according to any of Embodiments 37 to 43.

Embodiment 85. A radio access node (3300) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The radio access node including a processor (3310); and a memory (3320) coupled to the processor, wherein the memory stores instructions that when executed by the processor causes the processor to perform operations according to any of Embodiments 44 to 49.

Embodiment 86. A computer program product, including a non-transitory computer readable storage medium comprising computer readable program code embodied in the medium that when executed by a processor (3310) of a radio access node (3300) causes the processor to perform operations according to any of Embodiments 44 to 49.

Embodiment 87. A source radio access node (3300) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The source radio access node including a processor (3310); and a memory (3320) coupled to the processor, wherein the memory stores instructions that when executed by the processor causes the processor to perform operations according to any of Embodiments 50 to 59.

Embodiment 88. A computer program product, including a non-transitory computer readable storage medium comprising computer readable program code embodied in the medium that when executed by a processor (3310) of a source radio access node (3300) causes the processor to perform operations according to any of Embodiments 50 to 59.

Embodiment 89. A target radio access node (3300) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The target radio access node including a processor (3310); and a memory (3320) coupled to the processor, wherein the memory stores instructions that when executed by the processor causes the processor to perform operations according to any of Embodiments 60 to 68.

Embodiment 90. A computer program product, including a non-transitory computer readable storage medium comprising computer readable program code embodied in the medium that when executed by a processor (3310) of a target radio access node (3300) causes the processor to perform operations according to any of Embodiments 60 to 68.

Embodiment 91. A master radio access node (3300) for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network. The master radio access node including a processor (3310); and a memory (3320) coupled to the processor, wherein the memory stores instructions that when executed by the processor causes the processor to perform operations according to any of Embodiments 69 to 73.

Embodiment 92. A computer program product, including a non-transitory computer readable storage medium including computer readable program code embodied in the medium that when executed by a processor (3310) of a master radio access node (3300) causes the processor to perform operations according to any of Embodiments 69 to 73.

Further definitions and embodiments are discussed below:

In the above-description of various embodiments of present inventive concepts, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of present inventive concepts. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which present inventive concepts belong. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

When an element is referred to as being “connected”, “coupled”, “responsive”, or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being “directly connected”, “directly coupled”, “directly responsive”, or variants thereof to another element, there are no intervening elements present. Like numbers refer to like elements throughout. Furthermore, “coupled”, “connected”, “responsive”, or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term “and/or” includes any and all combinations of one or more of the associated listed items.

It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements/operations, these elements/operations should not be limited by these terms. These terms are only used to distinguish one element/operation from another element/operation. Thus a first element/operation in some embodiments could be termed a second element/operation in other embodiments without departing from the teachings of present inventive concepts. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification.

As used herein, the terms “comprise”, “comprising”, “comprises”, “include”, “including”, “includes”, “have”, “has”, “having”, or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof. Furthermore, as used herein, the common abbreviation “e.g.”, which derives from the Latin phrase “exempli gratia,” may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation “i.e.”, which derives from the Latin phrase “id est,” may be used to specify a particular item from a more general recitation.

Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).

These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks. Accordingly, embodiments of present inventive concepts may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as “circuitry,” “a module” or variants thereof.

It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated, and/or blocks/operations may be omitted without departing from the scope of inventive concepts. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. All such variations and modifications are intended to be included herein within the scope of present inventive concepts. Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of present inventive concepts. Thus, to the maximum extent allowed by law, the scope of present inventive concepts are to be determined by the broadest permissible interpretation of the present disclosure including the examples of embodiments and their equivalents, and shall not be restricted or limited by the foregoing detailed description.

Additional explanation is provided below.

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

FIG. 36: A wireless network in accordance with some embodiments.

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in FIG. 36. For simplicity, the wireless network of FIG. 36 only depicts network QQ106, network nodes QQ160 and QQ160 b, and WDs QQ110, QQ110 b, and QQ110 c (also referred to as mobile terminals). In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node QQ160 and wireless device (WD) QQ110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards or other 3GPP standards in future; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network QQ106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node QQ160 and WD QQ110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

In FIG. 36, network node QQ160 includes processing circuitry QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ187, and antenna QQ162. Although network node QQ160 illustrated in the example wireless network of FIG. 36 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node QQ160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium QQ180 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node QQ160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node QQ160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB's. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node QQ160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium QQ180 for the different RATs) and some components may be reused (e.g., the same antenna QQ162 may be shared by the RATs). Network node QQ160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ160.

Processing circuitry QQ170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry QQ170 may include processing information obtained by processing circuitry QQ170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry QQ170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node QQ160 components, such as device readable medium QQ180, network node QQ160 functionality. For example, processing circuitry QQ170 may execute instructions stored in device readable medium QQ180 or in memory within processing circuitry QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry QQ170 may include a system on a chip (SOC).

In some embodiments, processing circuitry QQ170 may include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174. In some embodiments, radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on the same chip or set of chips, boards, or units.

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry QQ170 executing instructions stored on device readable medium QQ180 or memory within processing circuitry QQ170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ170 alone or to other components of network node QQ160, but are enjoyed by network node QQ160 as a whole, and/or by end users and the wireless network generally.

Device readable medium QQ180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ170. Device readable medium QQ180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ170 and, utilized by network node QQ160. Device readable medium QQ180 may be used to store any calculations made by processing circuitry QQ170 and/or any data received via interface QQ190. In some embodiments, processing circuitry QQ170 and device readable medium QQ180 may be considered to be integrated.

Interface QQ190 is used in the wired or wireless communication of signalling and/or data between network node QQ160, network QQ106, and/or WDs QQ110. As illustrated, interface QQ190 comprises port(s)/terminal(s) QQ194 to send and receive data, for example to and from network QQ106 over a wired connection. Interface QQ190 also includes radio front end circuitry QQ192 that may be coupled to, or in certain embodiments a part of, antenna QQ162. Radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170. Radio front end circuitry may be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170. Radio front end circuitry QQ192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ198 and/or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162. Similarly, when receiving data, antenna QQ162 may collect radio signals which are then converted into digital data by radio front end circuitry QQ192. The digital data may be passed to processing circuitry QQ170. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node QQ160 may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192. Similarly, in some embodiments, all or some of RF transceiver circuitry QQ172 may be considered a part of interface QQ190. In still other embodiments, interface QQ190 may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).

Antenna QQ162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna QQ162 may be coupled to radio front end circuitry QQ190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna QQ162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna QQ162 may be separate from network node QQ160 and may be connectable to network node QQ160 through an interface or port.

Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry QQ187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160 with power for performing the functionality described herein. Power circuitry QQ187 may receive power from power source QQ186. Power source QQ186 and/or power circuitry QQ187 may be configured to provide power to the various components of network node QQ160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186 may either be included in, or external to, power circuitry QQ187 and/or network node QQ160. For example, network node QQ160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry QQ187. As a further example, power source QQ186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node QQ160 may include additional components beyond those shown in FIG. 36 that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node QQ160 may include user interface equipment to allow input of information into network node QQ160 and to allow output of information from network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE). a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE or other terminal implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device QQ110 includes antenna QQ111, interface QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136 and power circuitry QQ137. WD QQ110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD QQ110.

Antenna QQ111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ114. In certain alternative embodiments, antenna QQ111 may be separate from WD QQ110 and be connectable to WD QQ110 through an interface or port. Antenna QQ111, interface QQ114, and/or processing circuitry QQ120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna QQ111 may be considered an interface.

As illustrated, interface QQ114 comprises radio front end circuitry QQ112 and antenna QQ111. Radio front end circuitry QQ112 comprise one or more filters QQ118 and amplifiers QQ116. Radio front end circuitry QQ114 is connected to antenna QQ111 and processing circuitry QQ120, and is configured to condition signals communicated between antenna QQ111 and processing circuitry QQ120. Radio front end circuitry QQ112 may be coupled to or a part of antenna QQ111. In some embodiments, WD QQ110 may not include separate radio front end circuitry QQ112; rather, processing circuitry QQ120 may comprise radio front end circuitry and may be connected to antenna QQ111. Similarly, in some embodiments, some or all of RF transceiver circuitry QQ122 may be considered a part of interface QQ114. Radio front end circuitry QQ112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ118 and/or amplifiers QQ116. The radio signal may then be transmitted via antenna QQ111. Similarly, when receiving data, antenna QQ111 may collect radio signals which are then converted into digital data by radio front end circuitry QQ112. The digital data may be passed to processing circuitry QQ120. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry QQ120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD QQ110 components, such as device readable medium QQ130, WD QQ110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry QQ120 may execute instructions stored in device readable medium QQ130 or in memory within processing circuitry QQ120 to provide the functionality disclosed herein.

As illustrated, processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry QQ120 of WD QQ110 may comprise a SOC. In some embodiments, RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into one chip or set of chips, and RF transceiver circuitry QQ122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be on the same chip or set of chips, and application processing circuitry QQ126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry QQ122 may be a part of interface QQ114. RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry QQ120 executing instructions stored on device readable medium QQ130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ120 alone or to other components of WD QQ110, but are enjoyed by WD QQ110 as a whole, and/or by end users and the wireless network generally.

Processing circuitry QQ120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry QQ120, may include processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium QQ130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ120. Device readable medium QQ130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ120. In some embodiments, processing circuitry QQ120 and device readable medium QQ130 may be considered to be integrated. User interface equipment QQ132 may provide components that allow for a human user to interact with WD QQ110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to WD QQ110. The type of interaction may vary depending on the type of user interface equipment QQ132 installed in WD QQ110. For example, if WD QQ110 is a smart phone, the interaction may be via a touch screen; if WD QQ110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ132 is configured to allow input of information into WD QQ110, and is connected to processing circuitry QQ120 to allow processing circuitry QQ120 to process the input information. User interface equipment QQ132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment QQ132 is also configured to allow output of information from WD QQ110, and to allow processing circuitry QQ120 to output information from WD QQ110. User interface equipment QQ132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment QQ132, WD QQ110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

Auxiliary equipment QQ134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment QQ134 may vary depending on the embodiment and/or scenario.

Power source QQ136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD QQ110 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD QQ110 which need power from power source QQ136 to carry out any functionality described or indicated herein. Power circuitry QQ137 may in certain embodiments comprise power management circuitry. Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry QQ137 may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137 may perform any formatting, converting, or other modification to the power from power source QQ136 to make the power suitable for the respective components of WD QQ110 to which power is supplied.

FIG. 37: User Equipment in accordance with some embodiments

FIG. 37 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE QQ2200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE QQ200, as illustrated in FIG. 37, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although FIG. 37 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In FIG. 37, UE QQ200 includes processing circuitry QQ201 that is operatively coupled to input/output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ211, memory QQ215 including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and storage medium QQ221 or the like, communication subsystem QQ231, power source QQ233, and/or any other component, or any combination thereof. Storage medium QQ221 includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221 may include other similar types of information. Certain UEs may utilize all of the components shown in FIG. 37, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

In FIG. 37, processing circuitry QQ201 may be configured to process computer instructions and data. Processing circuitry QQ201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface QQ205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE QQ200 may be configured to use an output device via input/output interface QQ205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE QQ200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE QQ200 may be configured to use an input device via input/output interface QQ205 to allow a user to capture information into UE QQ200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

In FIG. 37, RF interface QQ209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface QQ211 may be configured to provide a communication interface to network QQ243 a. Network QQ243 a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243 a may comprise a Wi-Fi network. Network connection interface QQ211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface QQ211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM QQ217 may be configured to interface via bus QQ202 to processing circuitry QQ201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM QQ219 may be configured to provide computer instructions or data to processing circuitry QQ201. For example, ROM QQ219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium QQ221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium QQ221 may be configured to include operating system QQ223, application program QQ225 such as a web browser application, a widget or gadget engine or another application, and data file QQ227. Storage medium QQ221 may store, for use by UE QQ200, any of a variety of various operating systems or combinations of operating systems.

Storage medium QQ221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium QQ221 may allow UE QQ200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium QQ221, which may comprise a device readable medium.

In FIG. 37, processing circuitry QQ201 may be configured to communicate with network QQ243 b using communication subsystem QQ231. Network QQ243 a and network QQ243 b may be the same network or networks or different network or networks. Communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with network QQ243 b. For example, communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.QQ2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter QQ233 and/or receiver QQ235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter QQ233 and receiver QQ235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem QQ231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network QQ243 b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243 b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE QQ200.

The features, benefits and/or functions described herein may be implemented in one of the components of UE QQ200 or partitioned across multiple components of UE QQ200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem QQ231 may be configured to include any of the components described herein. Further, processing circuitry QQ201 may be configured to communicate with any of such components over bus QQ202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry QQ201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry QQ201 and communication subsystem QQ231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

FIG. 38: Virtualization environment in accordance with some embodiments

FIG. 38 is a schematic block diagram illustrating a virtualization environment QQ300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments QQ300 hosted by one or more of hardware nodes QQ330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

The functions may be implemented by one or more applications QQ320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications QQ320 are run in virtualization environment QQ300 which provides hardware QQ330 comprising processing circuitry QQ360 and memory QQ390. Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360 whereby application QQ320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment QQ300, comprises general-purpose or special-purpose network hardware devices QQ330 comprising a set of one or more processors or processing circuitry QQ360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory QQ390-1 which may be non-persistent memory for temporarily storing instructions QQ395 or software executed by processing circuitry QQ360. Each hardware device may comprise one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interface QQ380. Each hardware device may also include non-transitory, persistent, machine-readable storage media QQ390-2 having stored therein software QQ395 and/or instructions executable by processing circuitry QQ360. Software QQ395 may include any type of software including software for instantiating one or more virtualization layers QQ350 (also referred to as hypervisors), software to execute virtual machines QQ340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines QQ340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ350 or hypervisor. Different embodiments of the instance of virtual appliance QQ320 may be implemented on one or more of virtual machines QQ340, and the implementations may be made in different ways.

During operation, processing circuitry QQ360 executes software QQ395 to instantiate the hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer QQ350 may present a virtual operating platform that appears like networking hardware to virtual machine QQ340.

As shown in FIG. 38, hardware QQ330 may be a standalone network node with generic or specific components. Hardware QQ330 may comprise antenna QQ3225 and may implement some functions via virtualization. Alternatively, hardware QQ330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) QQ3100, which, among others, oversees lifecycle management of applications QQ320.

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, virtual machine QQ340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines QQ340, and that part of hardware QQ330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines QQ340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines QQ340 on top of hardware networking infrastructure QQ330 and corresponds to application QQ320 in FIG. 38.

In some embodiments, one or more radio units QQ3200 that each include one or more transmitters QQ3220 and one or more receivers QQ3210 may be coupled to one or more antennas QQ3225. Radio units QQ3200 may communicate directly with hardware nodes QQ330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signalling can be effected with the use of control system QQ3230 which may alternatively be used for communication between the hardware nodes QQ330 and radio units QQ3200.

FIG. 39: Telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.

With reference to FIG. 39, in accordance with an embodiment, a communication system includes telecommunication network QQ410, such as a 3GPP-type cellular network, which comprises access network QQ411, such as a radio access network, and core network QQ414. Access network QQ411 comprises a plurality of base stations QQ412 a, QQ412 b, QQ412 c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ413 a, QQ413 b, QQ413 c. Each base station QQ412 a, QQ412 b, QQ412 c is connectable to core network QQ414 over a wired or wireless connection QQ415. A first UE QQ491 located in coverage area QQ413 c is configured to wirelessly connect to, or be paged by, the corresponding base station QQ412 c. A second UE QQ492 in coverage area QQ413 a is wirelessly connectable to the corresponding base station QQ412 a. While a plurality of UEs QQ491, QQ492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station QQ412.

Telecommunication network QQ410 is itself connected to host computer QQ430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer QQ430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections QQ421 and QQ422 between telecommunication network QQ410 and host computer QQ430 may extend directly from core network QQ414 to host computer QQ430 or may go via an optional intermediate network QQ420. Intermediate network QQ420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network QQ420, if any, may be a backbone network or the Internet; in particular, intermediate network QQ420 may comprise two or more sub-networks (not shown).

The communication system of FIG. 39 as a whole enables connectivity between the connected UEs QQ491, QQ492 and host computer QQ430. The connectivity may be described as an over-the-top (OTT) connection QQ450. Host computer QQ430 and the connected UEs QQ491, QQ492 are configured to communicate data and/or signaling via OTT connection QQ450, using access network QQ411, core network QQ414, any intermediate network QQ420 and possible further infrastructure (not shown) as intermediaries. OTT connection QQ450 may be transparent in the sense that the participating communication devices through which OTT connection QQ450 passes are unaware of routing of uplink and downlink communications. For example, base station QQ412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer QQ430 to be forwarded (e.g., handed over) to a connected UE QQ491. Similarly, base station QQ412 need not be aware of the future routing of an outgoing uplink communication originating from the UE QQ491 towards the host computer QQ430.

FIG. 40: Host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to FIG. 40. In communication system QQ500, host computer QQ510 comprises hardware QQ515 including communication interface QQ516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system QQ500. Host computer QQ510 further comprises processing circuitry QQ518, which may have storage and/or processing capabilities. In particular, processing circuitry QQ518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer QQ510 further comprises software QQ511, which is stored in or accessible by host computer QQ510 and executable by processing circuitry QQ518. Software QQ511 includes host application QQ512. Host application QQ512 may be operable to provide a service to a remote user, such as UE QQ530 connecting via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the remote user, host application QQ512 may provide user data which is transmitted using OTT connection QQ550.

Communication system QQ500 further includes base station QQ520 provided in a telecommunication system and comprising hardware QQ525 enabling it to communicate with host computer QQ510 and with UE QQ530. Hardware QQ525 may include communication interface QQ526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system QQ500, as well as radio interface QQ527 for setting up and maintaining at least wireless connection QQ570 with UE QQ530 located in a coverage area (not shown in FIG. 40) served by base station QQ520. Communication interface QQ526 may be configured to facilitate connection QQ560 to host computer QQ510. Connection QQ560 may be direct or it may pass through a core network (not shown in FIG. 40) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware QQ525 of base station QQ520 further includes processing circuitry QQ528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station QQ520 further has software QQ521 stored internally or accessible via an external connection.

Communication system QQ500 further includes UE QQ530 already referred to. Its hardware QQ535 may include radio interface QQ537 configured to set up and maintain wireless connection QQ570 with a base station serving a coverage area in which UE QQ530 is currently located. Hardware QQ535 of UE QQ530 further includes processing circuitry QQ538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE QQ530 further comprises software QQ531, which is stored in or accessible by UE QQ530 and executable by processing circuitry QQ538. Software QQ531 includes client application QQ532. Client application QQ532 may be operable to provide a service to a human or non-human user via UE QQ530, with the support of host computer QQ510. In host computer QQ510, an executing host application QQ512 may communicate with the executing client application QQ532 via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the user, client application QQ532 may receive request data from host application QQ512 and provide user data in response to the request data. OTT connection QQ550 may transfer both the request data and the user data. Client application QQ532 may interact with the user to generate the user data that it provides.

It is noted that host computer QQ510, base station QQ520 and UE QQ530 illustrated in FIG. 40 may be similar or identical to host computer QQ430, one of base stations QQ412 a, QQ412 b, QQ412 c and one of UEs QQ491, QQ492 of FIG. 39, respectively. This is to say, the inner workings of these entities may be as shown in FIG. 40 and independently, the surrounding network topology may be that of FIG. 39.

In FIG. 40, OTT connection QQ550 has been drawn abstractly to illustrate the communication between host computer QQ510 and UE QQ530 via base station QQ520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE QQ530 or from the service provider operating host computer QQ510, or both. While OTT connection QQ550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection QQ570 between UE QQ530 and base station QQ520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments may improve the performance of OTT services provided to UE QQ530 using OTT connection QQ550, in which wireless connection QQ570 forms the last segment. More precisely, the teachings of these embodiments may improve the deblock filtering for video processing and thereby provide benefits such as improved video encoding and/or decoding.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection QQ550 between host computer QQ510 and UE QQ530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection QQ550 may be implemented in software QQ511 and hardware QQ515 of host computer QQ510 or in software QQ531 and hardware QQ535 of UE QQ530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection QQ550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software QQ511, QQ531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection QQ550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station QQ520, and it may be unknown or imperceptible to base station QQ520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer QQ510's measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software QQ511 and QQ531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection QQ550 while it monitors propagation times, errors etc.

FIG. 41: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

FIG. 41 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 39 and 40. For simplicity of the present disclosure, only drawing references to FIG. 41 will be included in this section. In step QQ610, the host computer provides user data. In substep QQ611 (which may be optional) of step QQ610, the host computer provides the user data by executing a host application. In step QQ620, the host computer initiates a transmission carrying the user data to the UE. In step QQ630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

FIG. 42: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

FIG. 42 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 39 and 40. For simplicity of the present disclosure, only drawing references to FIG. 42 will be included in this section. In step QQ710 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step QQ720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ730 (which may be optional), the UE receives the user data carried in the transmission.

FIG. 43: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

FIG. 43 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 39 and 40. For simplicity of the present disclosure, only drawing references to FIG. 43 will be included in this section. In step QQ810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data. In substep QQ821 (which may be optional) of step QQ820, the UE provides the user data by executing a client application. In substep QQ811 (which may be optional) of step QQ810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep QQ830 (which may be optional), transmission of the user data to the host computer. In step QQ840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

FIG. 44: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

FIG. 44 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 39 and 40. For simplicity of the present disclosure, only drawing references to FIG. 44 will be included in this section. In step QQ910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step QQ920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step QQ930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein. 

1. A method performed by a user equipment, UE, for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network, the method comprising: sending a session establishment request towards a session management node that includes an indication of a user plane integrity protection mode supported by the UE; and receiving an activation message from a receiving radio access node that includes an indication to the UE to activate the user plane integrity protection mode for a data radio bearer established with the receiving radio access node, wherein the receiving radio access node is an evolved long term evolution radio access node.
 2. (canceled)
 3. The method of claim 1, wherein the user plane integrity protection mode comprises one of: the UE supports user plane integrity protection in PDCP with a radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.
 4. The method of claim 1, wherein the radio access node is an evolved long term evolution radio access node.
 5. The method of claim 1, wherein the session management node comprises a session management function.
 6. A method performed by a user equipment, UE, for enabling user plane integrity protection of data during a mobility registration update procedure in a packet data convergence protocol, PDCP, in a radio access network, the method comprising: sending a registration request to a target core node that includes an indication that the UE supports a user plane integrity protection mode for communicating with a radio access node, wherein the radio access node is an evolved long term evolution radio access node.
 7. The method of claim 6, wherein the user plane integrity protection mode comprises one of: the UE supports user plane integrity protection in PDCP with the radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.
 8. The method of claim 6, further comprising: receiving a request from the target core node to resend the registration request including the indication that the UE supports the user plane integrity protection mode. 9.-14. (canceled)
 15. A method performed by a target access and mobility node for enabling user plane integrity protection of data during a mobility registration update procedure in a packet data convergence protocol, PDCP, in a radio access network, the method comprising: receiving a registration request from a user equipment, UE, that includes an indication that the UE supports a user plane integrity protection mode for communicating with a radio access node, wherein the radio access node is an evolved long term evolution radio access node.
 16. (canceled)
 17. The method of claim 15, wherein the user plane integrity protection mode comprises one of: the UE supports user plane integrity protection in PDCP with the radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate.
 18. The method of claim 15, further comprising: receiving a message from a source access and mobility node that includes the indication that the UE supports a user plane integrity protection mode.
 19. A method performed by a radio access node for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network, the method comprising: receiving a session information request from a core node that includes an indication of a user plane integrity protection mode supported by a user equipment, UE, wherein the radio access node is an evolved long term evolution radio access node.
 20. (canceled)
 21. The method of claim 19, wherein the user plane integrity protection mode comprises one of: the UE supports user plane integrity protection in PDCP with radio access node at a full data rate, and the UE supports user plane integrity protection in PDCP with the radio access node at a defined rate that is less than the full data rate
 22. The method of claim 19, further comprising: sending an activation message to the UE that includes the indication to the UE to activate user plane integrity protection for a data radio bearer established with a receiving radio access node.
 23. The method of claim 22, wherein the receiving access node is an evolved long term evolution radio access node.
 24. A user equipment for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network, the user equipment comprising: a processor; and a memory coupled to the processor, wherein the memory stores instructions that when executed by the processor causes the processor to perform operations comprising: send a session establishment request towards a session management node that includes an indication of a user plane integrity protection mode supported by the UE; and receive an activation message from a receiving radio access node that includes an indication to the UE to activate the user plane integrity protection mode for a data radio bearer established with the receiving radio access node, wherein the receiving radio access node is an evolved long term evolution radio access node.
 25. (canceled)
 26. (canceled)
 27. (canceled)
 28. A target access and mobility node for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network, the target access and mobility node comprising: a processor; and a memory coupled to the processor, wherein the memory stores instructions that when executed by the processor causes the processor to perform operations comprising: receive a registration request from a user equipment, UE, that includes an indication that the UE supports a user plane integrity protection mode for communicating with a radio access node, wherein the radio access node is an evolved long term evolution radio access node.
 29. (canceled)
 30. A radio access node for enabling user plane integrity protection of data in a packet data convergence protocol, PDCP, in a radio access network, the radio access node comprising: a processor; and a memory coupled to the processor, wherein the memory stores instructions that when executed by the processor causes the processor to perform operations comprising: receive a session information request from a core node that includes an indication of a user plane integrity protection mode supported by a user equipment, UE, wherein the radio access node is an evolved long term evolution radio access node.
 31. (canceled) 